You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarify when Mintlify recalculates a scheduled workflow's next run time, to match updated cron scheduling behavior in mintlify/server#6030.
Changes
Note that changing a workflow's schedule also resets the next run time to the current time.
Note that disabled workflows do not retain a pending run time.
Context
Upstream PR mintlify/server#6030 clears a cron workflow's stale next run time when the workflow is disabled or its trigger source changes, so it no longer fires on the previous schedule.
Note
Low Risk
Documentation-only wording in manage workflows; no product code or runtime behavior changes in this PR.
Overview
Updates the Disable a workflow note so scheduled (custom schedule) behavior matches server cron changes in mintlify/server#6030.
Re-enable or edit schedule: Mintlify now documents that changing a workflow’s schedule—not only turning it back on—recalculates the next run from the current time.
While disabled: The docs also state that disabled workflows do not keep a pending next run time, so users should not expect a stale schedule to fire after re-enabling or after trigger changes.
Reviewed by Cursor Bugbot for commit f531c72. Bugbot is set up for automated code reviews on this repo. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarify when Mintlify recalculates a scheduled workflow's next run time, to match updated cron scheduling behavior in mintlify/server#6030.
Changes
Context
Upstream PR mintlify/server#6030 clears a cron workflow's stale next run time when the workflow is disabled or its trigger source changes, so it no longer fires on the previous schedule.
Note
Low Risk
Documentation-only wording in manage workflows; no product code or runtime behavior changes in this PR.
Overview
Updates the Disable a workflow note so scheduled (custom schedule) behavior matches server cron changes in mintlify/server#6030.
Re-enable or edit schedule: Mintlify now documents that changing a workflow’s schedule—not only turning it back on—recalculates the next run from the current time.
While disabled: The docs also state that disabled workflows do not keep a pending next run time, so users should not expect a stale schedule to fire after re-enabling or after trigger changes.
Reviewed by Cursor Bugbot for commit f531c72. Bugbot is set up for automated code reviews on this repo. Configure here.